导航菜单
首页 >  Docker n8n Docs  > CLI commands

CLI commands

CLI commands for n8n#

n8n includes a CLI (command line interface), allowing you to perform actions using the CLI rather than the n8n editor. These include starting workflows, and exporting and importing workflows and credentials.

Running CLI commands#

You can use CLI commands with self-hosted n8n. Depending on how you choose to install n8n, there are differences in how to run the commands:

npm: the n8n command is directly available. The documentation uses this in the examples below.Docker: the n8n command is available within your Docker container:1docker exec -u node -it Start a workflow#

You can start workflows directly using the CLI.

Execute a saved workflow by its ID:

1n8n execute --id Change the active status of a workflow#

You can change the active status of a workflow using the CLI.

Restart required

These commands operate on your n8n database. If you execute them while n8n is running, the changes don't take effect until you restart n8n.

Set the active status of a workflow by its ID to false:

1n8n update:workflow --id= --active=false

Set the active status of a workflow by its ID to true:

1n8n update:workflow --id= --active=true

Set the active status to false for all the workflows:

1n8n update:workflow --all --active=false

Set the active status to true for all the workflows:

1n8n update:workflow --all --active=trueExport workflows and credentials#

You can export your workflows and credentials from n8n using the CLI.

Command flags:

FlagDescription--helpHelp prompt.--allExports all workflows/credentials.--backupSets --all --pretty --separate for backups. You can optionally set --output.--idThe ID of the workflow to export.--outputOutputs file name or directory if using separate files.--prettyFormats the output in an easier to read fashion.--separateExports one file per workflow (useful for versioning). Must set a directory using --output.--decryptedExports the credentials in a plain text format.Workflows#

Export all your workflows to the standard output (terminal):

1n8n export:workflow --all

Export a workflow by its ID and specify the output file name:

1n8n export:workflow --id= --output=file.json

Export all workflows to a specific directory in a single file:

1n8n export:workflow --all --output=backups/latest/file.json

Export all the workflows to a specific directory using the --backup flag (details above):

1n8n export:workflow --backup --output=backups/latest/Credentials#

Export all your credentials to the standard output (terminal):

1n8n export:credentials --all

Export credentials by their ID and specify the output file name:

1n8n export:credentials --id= --output=file.json

Export all credentials to a specific directory in a single file:

1n8n export:credentials --all --output=backups/latest/file.json

Export all the credentials to a specific directory using the --backup flag (details above):

1n8n export:credentials --backup --output=backups/latest/

Export all the credentials in plain text format. You can use this to migrate from one installation to another that has a different secret key in the configuration file.

Sensitive information

All sensitive information is visible in the files.

1n8n export:credentials --all --decrypted --output=backups/decrypted.jsonImport workflows and credentials#

You can import your workflows and credentials from n8n using the CLI.

Update the IDs

When exporting workflows and credentials, n8n also exports their IDs. If you have workflows and credentials with the same IDs in your existing database, they will be overwritten. To avoid this, delete or change the IDs before importing.

Available flags:

FlagDescription--helpHelp prompt.--inputInput file name or directory if you use --separate.--projectIdImport the workflow or credential to the specified project. Can't be used with --userId.--separateImports *.json files from directory provided by --input.--userIdImport the workflow or credential to the specified user. Can't be used with --projectId.

Migrating to SQLite

n8n limits workflow and credential names to 128 characters, but SQLite doesn't enforce size limits.

This might result in errors like Data too long for column name during the import process.

In this case, you can edit the names from the n8n interface and export again, or edit the JSON file directly before importing.

Workflows#

Import workflows from a specific file:

1n8n import:workflow --input=file.jsonImport all the workflow files as JSON from the specified directory:1n8n import:workflow --separate --input=backups/latest/Credentials#

Import credentials from a specific file:

1n8n import:credentials --input=file.json

Import all the credentials files as JSON from the specified directory:

1n8n import:credentials --separate --input=backups/latest/License#Clear#

Clear your existing license from n8n's database and reset n8n to default features:

1n8n license:clearInfo#

Display information about the existing license:

1n8n license:infoUser management#

You can reset user management using the n8n CLI. This returns user management to its pre-setup state. It removes all user accounts.

Use this if you forget your password, and don't have SMTP set up to do password resets by email.

1n8n user-management:resetDisable MFA for a user#

If a user loses their recovery codes you can disable MFA for a user with this command. The user will then be able to log back in to set up MFA again.

1n8n mfa:disable --email=johndoe@example.comDisable LDAP#

You can reset the LDAP settings using the command below.

1n8n ldap:resetSecurity audit#

You can run a security audit on your n8n instance, to detect common security issues.

1n8n audit

相关推荐: